User interfaces for updating network connection settings of external devices

ABSTRACT

The present disclosure generally relates to managing network connection settings of external devices. In some embodiments, an electronic device with a display and one or more wireless antennas, while the electronic device is connected, via the one or more wireless antennas, to a first local area network, displays a first external device management interface, wherein: the first external device management interface is associated with a first external device that is not connected to the first local area network; and the first external device management interface includes a first affordance. The electronic device receives a user input corresponding to selection of the first affordance and, in response to receiving the user input corresponding to selection of the first affordance, causes the first external device to connect to the first local area network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.62/679,947, entitled “USER INTERFACES FOR UPDATING NETWORK CONNECTIONSETTINGS OF EXTERNAL DEVICES”, filed Jun. 3, 2018, the entire contentsof which are hereby incorporated by reference.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing network connectionsettings of an external device.

BACKGROUND

The number of electronic devices, and particularly smart devices, inusers' homes continues to increase. These devices are increasingly beinginterconnected with each other, are increasingly more capable, and areperforming more complex tasks. As such, these devices are increasinglyexpected to have thoughtfully-designed user interfaces.

BRIEF SUMMARY

Some techniques for managing network connection settings of an externaldevice using electronic devices, however, are generally cumbersome andinefficient. For example, some existing techniques use a complex andtime-consuming user interface, which may include multiple key presses orkeystrokes. For further example, some existing techniques do not provideany notification relating to potential issues with a network setting ofan external device. Existing techniques require more time thannecessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managing networkconnection settings of an external device. Such methods and interfacesoptionally complement or replace other methods for managing networkconnection settings of an external device. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. Such methods and interfaces can reduce thenumber of unnecessary, extraneous, or repetitive user inputs formanaging network settings of an external device. For battery-operatedcomputing devices, such methods and interfaces conserve power andincrease the time between battery charges.

In accordance with some embodiments, a method is performed at a devicewith a display and one or more wireless antennas. The method comprises:while the electronic device is connected, via the one or more wirelessantennas, to a first local area network, displaying a first externaldevice management interface, wherein: the first external devicemanagement interface is associated with a first external device that isnot connected to the first local area network; and the first externaldevice management interface includes a first affordance; receiving auser input corresponding to selection of the first affordance; and inresponse to receiving the user input corresponding to selection of thefirst affordance, causing the first external device to connect to thefirst local area network.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display and one ormore wireless antennas, the one or more programs including instructionsfor: while the electronic device is connected, via the one or morewireless antennas, to a first local area network, displaying a firstexternal device management interface, wherein: the first external devicemanagement interface is associated with a first external device that isnot connected to the first local area network; and the first externaldevice management interface includes a first affordance; receiving auser input corresponding to selection of the first affordance; and inresponse to receiving the user input corresponding to selection of thefirst affordance, causing the first external device to connect to thefirst local area network.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: a display; one or more wirelessantennas; one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: while the electronicdevice is connected, via the one or more wireless antennas, to a firstlocal area network, displaying a first external device managementinterface, wherein: the first external device management interface isassociated with a first external device that is not connected to thefirst local area network; and the first external device managementinterface includes a first affordance; receiving a user inputcorresponding to selection of the first affordance; and in response toreceiving the user input corresponding to selection of the firstaffordance, causing the first external device to connect to the firstlocal area network.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: a display; one or more wirelessantennas; while the electronic device is connected, via the one or morewireless antennas, to a first local area network, means for displaying afirst external device management interface, wherein: the first externaldevice management interface is associated with a first external devicethat is not connected to the first local area network; and the firstexternal device management interface includes a first affordance; meansfor receiving a user input corresponding to selection of the firstaffordance; and means for, responsive to receiving the user inputcorresponding to selection of the first affordance, causing the firstexternal device to connect to the first local area network.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display and one or morewireless antennas, the one or more programs including instructions for:while the electronic device is connected, via the one or more wirelessantennas, to a first local area network, displaying a first externaldevice management interface, wherein: the first external devicemanagement interface is associated with a first external device that isnot connected to the first local area network; and the first externaldevice management interface includes a first affordance; receiving auser input corresponding to selection of the first affordance; and inresponse to receiving the user input corresponding to selection of thefirst affordance, causing the first external device to connect to thefirst local area network.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing network connection settings of an externaldevice, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for managing network connectionsettings of an external device.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIG. 5I illustrates an electronic device in accordance with someembodiments.

FIG. 5J is a block diagram illustrating an electronic device inaccordance with some embodiments.

FIGS. 6A-6G illustrate exemplary techniques and user interfaces forconfiguring an electronic device in accordance with some embodiments.

FIGS. 7A-7J illustrate exemplary techniques and user interfaces forconfiguring an electronic device in accordance with some embodiments.

FIGS. 8A-8C is a flow diagram illustrating a process for configuring anelectronic device in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing network connection settings of an externaldevice. For example, there is a need for methods and interfaces thatprovide the ability to resolve a mismatch between network connectionsettings between two devices. Such techniques can reduce the cognitiveburden on a user who manages network connection settings of an externaldevice, thereby enhancing productivity. Further, such techniques canreduce processor and battery power otherwise wasted on redundant userinputs.

Below, FIGS. 1A-1B, 2, 4A-4B, and 5A-5J provide a description ofexemplary devices for performing the techniques for managing networkconnection settings of an external device. FIGS. 6A-6G illustrateexemplary techniques and user interfaces for configuring an electronicdevice. FIGS. 7A-7J illustrate exemplary techniques and user interfacesfor configuring an electronic device. FIGS. 8A-8C is a flow diagramillustrating a process for configuring an electronic device inaccordance with some embodiments. The user interfaces in FIGS. 6A-6G and7A-7J are used to illustrate the processes described below, includingthe processes in FIGS. 8A-8C.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NEC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Patents: U.S. Pat. No. 6,323,846 (Westerman etal.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No.6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1,each of which is hereby incorporated by reference in its entirety.However, touch screen 112 displays visual output from device 100,whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed. May2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737; “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in PO subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. Nos. 11/241,839,“Proximity Detector In Handheld Device”; 11/240,788, “Proximity DetectorIn Handheld Device”; 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; 11/586,862, “Automated Response To And SensingOf User Activity In Portable Devices”; and 11/638,251, “Methods AndSystems For Automatic Configuration Of Peripherals,” which are herebyincorporated by reference in their entirety. In some embodiments, theproximity sensor turns off and disables touch screen 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation., contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132. receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata.;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets)

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RIF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using) XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147 the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which should.handle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152;            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for LM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar,”        -   Icon 428 for image management module 144, labeled “Photos;”        -   icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video,”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather,”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In sonicembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, and 3. Device 500 has bus 512 thatoperatively couples I/O section 514 with one or more computer processors516 and memory 518. I/O section 514 can be connected to display 504,which can have touch-sensitive component 522 and, optionally, intensitysensor 524 (e.g., contact intensity sensor). In addition, I/O section514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 is, optionally, a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 508is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including process 800 (FIG.8A-8C). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIG. 5I illustrates exemplary electronic device 580. Device 580 includesbody 580A. In some embodiments, device 580 can include some or all ofthe features described with respect to devices 100, 300, and 500 (e.g.,FIGS. 1A-5B). In some embodiments, device 580 has one or more speakers580B (concealed in body 580A), one or more microphones 580C, one or moretouch-sensitive surfaces 580D, and one or more displays 580E.Alternatively, or in addition to a display and touch-sensitive surface580D, the device has a touch-sensitive display (also referred to as atouchscreen). As with devices 100, 300, and 500, in some embodiments,touch-sensitive surface 580D (or the touch screen) optionally includesone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors oftouch-sensitive surface 580D (or the touchscreen) can provide outputdata that represents the intensity of touches. The user interface ofdevice 580 can respond to touches based on their intensity, meaning thattouches of different intensities can invoke different user interfaceoperations on device 580. In some embodiments, the one or more displays580E are one or more light-emitting diodes (LEDs). For example, adisplay can be a single LED, an LED cluster (e.g., a red, a green, and ablue LED), a plurality of discrete LEDs, a plurality of discrete LEDclusters, or other arrangement of one or more LEDs. For example, thedisplay 580E can be an array of nine discrete LED clusters arranged in acircular shape (e.g., a ring). In some examples, the one or moredisplays are comprised of one or more of another type of light-emittingelements.

FIG. 5J depicts exemplary personal electronic device 580. In someembodiments, device 580 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B and 5A-5B. Device 580 has bus 592that operatively couples I/O section 594 with one or more computerprocessors 596 and memory 598. I/O section 594 can be connected todisplay 582, which can have touch-sensitive component 584 and,optionally, intensity sensor 585 (e.g., contact intensity sensor). Insome embodiments, touch-sensitive component 584 is a separate componentthan display 582. In addition, I/O section 594 can be connected withcommunication unit 590 for receiving application and operating systemdata, using Wi-Fi, Bluetooth, near field communication (NFC), cellular,and/or other wireless communication techniques. Device 580 can includeinput mechanisms 588. Input mechanism 588 is, optionally, a button, insome examples. Input mechanism 588 is, optionally, a microphone, in someexamples. Input mechanism 588 is, optionally, a plurality of microphones(e.g., a microphone array).

Electronic device 580 includes speaker 586 for outputting audio. Device580 can include audio circuitry (e.g., in I/O section 594) that receivesaudio data, converts the audio data to an electrical signal, andtransmits the electrical signal to speaker 586. Speaker 586 converts theelectrical signal to human-audible sound waves. The audio circuitry(e.g., in I/O section 594) also receives electrical signals converted bya microphone (e.g., input mechanism 588) from sound waves. The audiocircuitry (e.g., in I/O section 594) converts the electrical signal toaudio data. Audio data is, optionally, retrieved from and/or transmittedto memory 598 and/or RF circuitry (e.g., in communication unit 590) byI/O section 594.

Memory 598 of personal electronic device 580 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 596, for example, can cause the computer processorsto perform the techniques described below, including process 800 (FIG.8A-8C). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages, Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 580is not limited to the components and configuration of FIG. 5J, but caninclude other or additional components in multiple configurations.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6G illustrate exemplary user interfaces for using a firstdevice to configure a second device, in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIG. 8A-8C.

FIG. 6A illustrates a scenario in which a user brings device 600 intoclose proximity to device 606. In this example, device 600 is being usedto configure device 606 (e.g., an initial configuration after poweringon device 606 for the first time). In some embodiments, device 606includes one or more features of device 580 as described above. In someembodiments, device 606 includes one or more features of device 100,300, or 500. In some embodiments, device 600 includes one or morefeatures of device 100, 300, or 500. In this example, device 600 is asmartphone device and device 606 is a smart speaker device (alsoreferred to as a “network connected speaker”).

As shown in FIG. 6A, device 606 has limited display capabilities, andthus configuration of device 606 can be made easier by the use ofanother device 600 having more robust display capabilities. In someembodiments, device 606 is a smart home device (e.g., a networkconnected speaker) that a user places within their home (e.g., in onelocation, or moving between many locations). In such case, the user hasphysical access to the device when configuring it, and thus the use ofphysical proximity can be used as part of an intuitive and easy to useinterface for configuring the device 606. Thus, rather than making auser navigate various menus attempting to establish or accesscommunication between a personal device (e.g., device 600) and thedevice 606, a user can place their personal device near device 606 asshown in FIG. 6A, for example, as part of a configuration process.

As shown in FIG. 6A, device 606 is outputting an audio tone signal 604(e.g., representing sound waves). In some embodiments, device 606outputs an audio tone signal (e.g., 604) in response to an indicationthat device 600 is in close proximity to device 606. In someembodiments, device 600 outputs an audio tone signal (not illustrated)in response to an indication that device 600 is in close proximity todevice 606. In some embodiments, the audio tone signals from devices 600and 606 are synchronized (e.g., are outputted concurrently). In someembodiments, one of the audio tone signals are staggered in time (e.g.,device 600 plays a tone first, followed by device 606). In someembodiments, the audio tone signals are harmonically related orcompatible.

In some embodiments, an audio tone signal is only output by one device(e.g., to be configured, such as device 606) that is in close proximityto device 600, other than device 600. For example, in some situations,device 600 is placed in close proximity to multiple other devices thatcan be configured using device 600. For example, a user may havepurchased two speakers (e.g., such as device 606) and wishes toconfigure one of them. In such case, it is useful to the user to beaware of which speaker device 600 has connected to and that will beconfigured, for example, according to the techniques described below.Thus, even though device 600 is brought into close proximity to twoconfigurable devices, only the configurable device (e.g., device 606)that will be configured during the configuration process will output anaudio tone in response to an indication that device 600 is in closeproximity.

FIG. 6B depicts an exemplary state of device 600 immediately prior tobeing placed in close proximity to device 606. As shown in FIG. 6B,device 600 displays a home screen 605 on display 602. At FIG. 6C, device600 is placed into close proximity to device 606 (e.g., is within theproximity zone 608).

FIG. 6C includes a proximity condition range indicator 608. A proximitycondition range indicator is also referred to herein as a “proximityzone indicator” or simply as a “proximity zone”. In FIG. 6C, device 600is within the area indicated by proximity condition range indicator 608(e.g., is within a threshold distance to device 606). Proximitycondition range indicator 608 is included as a visual aid, and isintended to represent a physical proximity (threshold distance) thatwould satisfy a proximity condition. For example, proximity conditionrange indicator 608 can represent the range of a near-fieldcommunication detection circuitry of device 606. In some embodiments,any appropriate technique can be used to detect proximity betweendevices. For example, Bluetooth Low Energy is used. For example,peer-to-peer Wi-Fi can is used. For example, wide-band wirelessconnection is used. Wide-band wireless connection is used, for example,to determine one or more of: directionality, distance, and orientation,of one or more devices. Thus, presence of a detectable device within(e.g., partially or completely) within a threshold distance representedby the proximity condition range indicator 608 would satisfy a proximitycondition, but would not if the detectable device is located outside ofthe range indicator 608. One of skill would appreciate that a detectionrange of physical proximity can be non-uniform, can be affected bynumerous variables (e.g., wireless interference, air humidity, or thelike), and can include points in space in three dimensions, all of whichare intended to be within the scope of this disclosure. Thus, thegraphical representation of proximity condition range indicator 608 isnot intended to limit the scope of determining whether a proximitycondition is satisfied.

As shown in FIG. 6C, device 606 and device 600 are close together anddevice 600 is at least partially within the proximity condition rangeindicator 608. Because proximity condition range indicator 608represents a physical proximity that satisfies the proximity condition,the first device 606 detects an indication that a physical proximitybetween the first device and the second device 600 satisfies theproximity condition. In some examples, in accordance with detecting thata proximity condition is satisfied, device 606 initiates a configurationprocess. For example, the device 606 can enter a configuration mode forreceiving configuration data (e.g., settings, account information, andthe like) from device 600. In sonic examples, in accordance withdetecting that a proximity condition is satisfied, device 606 proceedsto a next step in a configuration process. For example, if the device606 is already in a configuration mode, the satisfaction of a proximitycondition can cause the device 606 to proceed to a next step. Forinstance, satisfaction of the proximity condition can be required inorder to verify the identity of the second device or verify that theuser of device 600 has physical access to device 606 (e.g., is not auser outside of the home that is attempting to remotely access andconfigure device 606).

In some embodiments, in response to detecting an indication that device600 entered into close proximity to device 606 (e.g., satisfied aproximity condition), device 600 displays proximity card 610, as shownin FIG. 6D.

FIGS. 6D-6G illustrate exemplary interfaces of a configuration process,in accordance with some embodiments. In this example, the configurationprocess is a process for configuring a second device using a firstdevice. Thus, as shown, the interfaces are displayed on a first device(e.g., device 600), and the steps of the configuration process pertainto, for example, transmitting data to the second device (e.g., 606),selecting or entering configuration settings at the first device, andthe like. In some embodiments, the steps shown in FIGS. 6D-6G can bedisplayed in any order (e.g., other than that shown or describedherein). In some embodiments, one or more of the steps shown in FIG.6D-6G are omitted from a configuration process. In some embodiments, oneor more steps other than those shown in FIG. 6D-6G are included in aconfiguration process. In some embodiments, the first device and thesecond device are devices that include one or more features of devices100, 300, 500, or 580.

FIG. 6D illustrates an exemplary setup card. In some embodiments, device600 displays setup card 610 in response to being placed in closeproximity to device 606. Thus, a setup card is also referred to hereinas a “proximity card”. In some embodiments, a device continuesdisplaying a setup or proximity card after being removed from closeproximity to another device. In some embodiments, device 600 displayssetup card 610 in response to user input representing a request toinitiate a configuration process of an external device (e.g., 606). Forexample, user input selection of a displayed affordance (e.g., withoutrequiring proximity) can cause setup card 610 to be displayed.

As shown in FIG. 6D, setup card 610 includes an identification of thedevice to be configured, which is the device (e.g., 606) that device 600was placed in close proximity to. As shown, setup card 610 includes thetitle “Speaker” (e.g., device 606 is a smart speaker), as well as animage depicting the device (e.g., in the shape of device 606 as shown inFIG. 6A). Setup card 610 also includes affordance 610A. In someembodiments, device 600 initiates a configuration process (or otherwiseproceeds to a next step in a configuration process) in response toreceiving selection of affordance 610A. During the configurationprocess, device 600 can display interfaces for configuring variousfeatures of device 606, including a voice assistant function, profileinformation, and network connection settings.

FIG. 6E illustrates an exemplary interface for sharing settings that canbe displayed during a configuration process. Setup card 620 of FIG. 6Eincludes a prompt to the user to share settings with device 606 (“ShareSettings”). In some embodiments, a prompt to share settings includes anindication of the settings to be shared. For example, setup card 620includes graphical depictions representing the settings that will beshared between device 606 and device 600 (e.g., music data, calendardata, home data, or the like). In some embodiments, the settings sharedare copied from the settings of the first device (e.g., 600). Forexample, device 600 configures device 606 to use preferences, profiles,and/or settings already associated with device 600. This can save theuser the time and effort needed to manually select their preferredsettings that already exist on device 600. In some embodiments, theshared settings data includes data configuring the second device (e.g.,606) to use a particular local area network (e.g., a Wi-Fi network). Forexample, in response to selection of affordance 620A, device 600configures device 606 to connect to the Wi-Fi network that is being usedby device 600 during the configuration process. In this example, device600 configures device 606 to use the Wi-Fi network having the serviceset identifier (“SSID”): “OLD_NETWORK”. For example, device 600transmits (to device 606) the SSID of the network, along with anytokens, keys, or passwords necessary to gain access to the network“OLD_NETWORK”, if the network is secured.

In some embodiments, device 600 transmits the settings information todevice 606 in response to user input selection of the affordance 620A(labeled “Share Settings”) of card 620. In some embodiments, in responseto user input selection of the “Share Settings” affordance 620A of card620, device 600 displays setup card 630 (FIG. 6F).

At FIG. 6F, device 600 displays setup card 630. In some embodiments,device 600 displays setup card 630 in response to user input selectionof affordance 620A. In some examples, setup card 630 is displayed whiledevice 600 exchanges data with device 606 (e.g., device 600 istransmitting settings data as described above). For example, setup card630 includes status 630A showing that the devices are connecting (orotherwise exchanging data).

FIG. 6G illustrates an exemplary interface after successfulconfiguration of a second device by a first device. FIG. 6G depictssetup card 640, which includes an indication of the user's name. In thisexample, the user (“John”) is greeted by name (“Hi, John!”), indicatingthat device 606 successfully received the user's account data and/orother settings data. Device 600 optionally displays setup card 640 aftersetup card 630. In some embodiments, setup card 640, includes adepiction of device 606 and a check mark icon, indicating a successfuldata transfer (e.g., settings were successfully shared) or configuration(e.g., configuration is complete). In some embodiments, device 600displays setup card 640 in response to user input representing a requestto share settings (e.g., selection of affordance 620A).

Accordingly, upon successful configuration of device 606 with thesettings of device 600, device 606 is configured to connect to thewireless network with the SSID “OLD_NETWORK”. However, there may besituations in which the user would like to alter the network settings ofthe configured external device after the configuration process iscomplete, but without repeating the entire initial configuration process(e.g., which can involve deleting all settings on device 606). Forexample, the user of devices 600 and 606 can desire to make such achange to the network settings of the external device if they change theSSID of their home wireless network, if they move device 606 (e.g.,temporarily) to a new location, or if their device 600 was connected tothe wrong wireless network during the initial configuration process(e.g., inadvertently). Techniques and interfaces for doing so are nowdiscussed.

FIGS. 7A-7J illustrate exemplary interfaces for configuring a networksetting of an external electronic device. The interfaces can bedisplayed by a first electronic device and used to, for example, changethe network settings of a second, external electronic device subsequentto completing configuration of the second electronic device. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 8A-8C.

FIG. 7A illustrates electronic device 600 with touch-sensitive display602. In FIG. 7A, device 600 displays a home user interface 700 of anapplication for managing devices (e.g., controllable devices) associatedwith a location 123 Main St. Home user interface 704 includes, interalia, the name of the location (123 Main St.), a device representation702 corresponding to a second electronic device (e.g., device 606), adevice representation 704 corresponding to a third electronic device(e.g., a smart home device that is a lamp), a status message 706, and astatus detail affordance 708.

As shown in FIG. 7A, device representation 702 represents an externalelectronic device, device 606. In this example, device 606 wasconfigured in accordance with the setup process described above withrespect to FIGS. 6A-6G. Thus, device 606 was configured with thewireless network settings of device 600 at the time of configuration,and is currently connected to the Wi-Fi network having the Wi-Fi SSID“OLD_NETWORK”.

Device 600 can allow a user to subsequently (e.g., after the initialconfiguration) modify which local area network (e.g., Wi-Fi network)that device 606 connects to.

In some embodiments, the device (e.g., 600) displays an indication ifthe external device (e.g., 606) is connected to a different local areanetwork than the device. For instance, in this example, device 600 isnow currently connected to a local area network having the Wi-Fi SSID“NEW_NETWORK”. Thus, as shown in FIG. 7A, home user interface 700includes status message 706, which notifies of a mismatch between thelocal area network settings of the device (e.g., 600) and an externaldevice (e.g., 606) specifically, that a device (e.g., device 606)associated with the location and device 600 are respectively connectedto different Wi-Fi networks. Status message 706 in FIG. 7A reads: “SOMEACCESSORIES ARE ON A DIFFERENT WI-FI NETWORK THAN THIS PHONE”.

In some embodiments, a device representation (e.g., 702) correspondingto an external device includes a status message (e.g., 702A) identifyinga mismatch between the network settings of the device (e.g., 600) andthe corresponding external device (e.g., 606). For example, in FIG. 7A,device representation 702. Includes a status message 702A (e.g., and anexclamation icon) notifying that there is an issue with the Wi-Finetwork settings of device 606.

In some embodiments, a status message (e.g., 706, 702A) is displayed ina different color than surrounding text. For example, the status message702A can be displayed in a red color, while text surrounding text isblack or grey, drawing the user's attention to the message.

In some embodiments, a status message (e.g., 706, 702A) is displayedonly when the device (e.g., 600) and the external device (e.g., 606) arewithin a threshold proximity to each other. For example, if both device600 and device 606 are connected to the Internet, device 600 can accessand display the status of device 606 (e.g., at a home user interface),even when the devices are not in close proximity (e.g., device 600 iswith the user at their place of work, and device 606 remains in theuser's home several miles away from work). Given the distance, it is tobe expected that the devices will be connected to different local areanetworks (e.g., device 600 is connected to the user's work network, anddevice 606 remains connected to the user's home network). In this way,when the user accesses home user interface 700 on device 600, they arenot presented an irrelevant status message 706 notifying of a mismatchbetween the respective local area networks then being used by device 600and device 606. In some embodiments, threshold proximity is determinedbased on the devices being within the range of each other based on oneor more of: Bluetooth (e.g., Bluetooth Low Energy) range or peer-to-peerWi-Fi range. For example, device 600 detects that it is withinpeer-to-peer Wi-Fi range of device 606, and that device 606 is connectedto a different wireless network, and thus displays status message 706 athome status interface 700. The threshold proximity used to conditionallydisplay a status message (e.g., 706, 702A) can be the same or different(e.g., greater) than a threshold proximity used to initiate aconfiguration process, as described above with respect to FIGS. 6A-6G.

In FIG. 7B, device 600 receives (e.g., detects) user input 710 (e.g., atap) representing selection of a status detail affordance 708 and, inresponse, displays home status interface 712 as shown in FIG. 7C. Insome embodiments, user input representing selection of a status message(e.g., 706) causes the device to display a home status interface (e.g.,712).

FIG. 7C illustrates an exemplary home status interface 712. In someembodiments, a home status interface (e.g., 712) includes the status ofone or more devices (e.g., 606) associated with the location (e.g., 123Main St.) associated with the application for managing devices. In thisexample, home status interface 712 includes status message 716,identifying a mismatch between the network settings of the device (e.g.,600) and one or more accessories devices) associated with the location(e.g., such as external device 606). Message 716 is similar to, and caninclude the features as described herein with respect to message 706. InFIG. 7C, message provides more detail (than message 706), and identifiesthe specific device(s) (in this example, the device named “SPEAKER”)that has a mismatch of Wi-Fi with device 600. Message 716 reads:“SPEAKER: THIS ACCESSORY IS ON A DIFFERENT WI-FI NETWORK THAN THISPHONE. MOVE SPEAKER TO THE NETWORK THIS PHONE IS ON”. In someembodiments, a home status interface includes one or more devicerepresentations (e.g., 702). For example, home status interface 712 alsoincludes device representation 702 associated with device 606, anddevice representation 704 associated with a smart device that is a lamp(e.g., that can be turned on or off using the application). In FIG. 7C,home status interface 712 includes device status information associatedwith a respective device representation. For example, devicerepresentation 702 includes status message 702A, and devicerepresentation 704 includes the status of the lamp (“OFF”).

In some embodiments, a home status interface includes an area thatincludes one or more device representations of devices that areassociated with a particular status (e.g., an error condition orabnormal status). For example, in FIG. 7C, home status interface 712includes the area labeled with the heading “ATTENTION”, and includesdevice representation 702 and status message 702A, indicating the Wi-Fimismatch. Note that the remaining device representations (e.g., 704)with normal statuses (e.g., “OFF”, “STREAMING”), are presented belowdevice representation 702, and not in the area labeled “ATTENTION”. Insome embodiments, status message 716 is relevant to two or more devicesidentified having a mismatch in network settings. For example, if therewere two devices with a network mismatch, message 716 can identify thisissue and read “SPEAKER 1 AND SPEAKER 2: THESE ACCESSORIES ARE ON ADIFFERENT WI-FI NETWORK THAN THIS PHONE. MOVE THESE SPEAKERS TO THENETWORK THIS PHONE IS ON.” In such embodiments, representations of eachof the two or more devices having a mismatch can be displayed under theindication “ATTENTION”.

In some embodiments, status interface 712 is displayed without anaffordance for changing the network setting of one or more externaldevices. In such embodiments, affordance 732 of FIG. 7E is the primary(or only) affordance for causing a network setting of the externaldevice (e.g., 606) to be updated.

In some embodiments, at least a portion of a status message (e.g., 716)is an affordance for changing a network setting of one or more externaldevices. For example, at least a portion (e.g., the portion with text“MOVE THIS SPEAKER TO THE NETWORK THE PHONE IS ON”) of message 716 canbe selectable to cause the Wi-Fi mismatch to be resolved. In someembodiments, a status message (e.g., 716) is displayed concurrently withan affordance for changing a network setting of one or more externaldevices. For example, status message 716 can be displayed adjacent to aseparate affordance. In some embodiments, a device (e.g., 600) receivesuser input representing selection of an affordance (e.g., 716) forchanging a network setting of an external device (e.g., 606) displayedat a home status interface (e.g., 712) and, in response, causes anetwork setting of the external device (e.g., 606) to be updated. Forexample, user input representing selection of affordance 716 at homestatus interface 712 can cause device 600 to perform any of thefunctions described below with respect to selection of affordance 732 ofFIG. 7E. For instance, device 600 can cause device 606 be connected tothe network with the SKID “NEW_NETWORK” in response to receivingselection of affordance 716. In some embodiments, in response toreceiving user input selection of an affordance (e.g., 713) at a homestatus interface, a device (e.g., 600) displays a device detailinterface (e.g., 730). For example, in response to receiving selectionof affordance 716, device 600 displays device detail interface 730 asshown in either of FIGS. 7E, 7F, or 7G.

At FIG. 7C, device 600 receives user input 714 corresponding toselection of device representation 702. In this example, user input 714is a deep press (e.g., a touch with a characteristic intensity thatexceeds an intensity threshold that is greater than a touch detectionintensity threshold). User input 714 can also be a tap gesture, or a tapand hold (e.g., a touch exceeding a threshold duration).

FIG. 7D illustrates an exemplary device status interface 720. Forexample, device 600 displays device status user interface 720 inresponse to receiving user input 714. Device status interface 720includes a status message about the current status of external device606 (named “FAMILY ROOM SPEAKER”), which includes a status message 726notifying of a mismatch between the network settings of the device(e.g., 600) and the external device (e.g., 606). Notably, status message726 specifically identifies that the currently selected device 606 isconnected to a different Wi-Fi network than the device 600 displayingstatus interface 720: “THIS SPEAKER IS ON A DIFFERENT WI-FI NETWORK THANTHIS PHONE”. Device status interface 720 also includes affordance 724,for accessing additional details regarding corresponding device 606, Asshown in FIG. 7D, device 600 receives user input 726 (e.g., a tap)corresponding to selection of affordance 724.

FIG. 7E illustrates an exemplary device detail interface 730. Forexample, device detail interface 730 is displayed in response to userinput 726. In another example, device detail interface 730 is displayedin response to user input at a home status interface (e.g., 712), suchas selection (e.g., deep press) of device representation 702. In someembodiments, a device detail interface includes one or more of statusmessages, identifying information, and options for configuring thesettings of the corresponding external device (e.g., 606). In thisexample, device detail interface 730 includes device representation 702,that also includes status message 702A, which is displayed in red.

As shown in FIG. 7E, device detail interface 730 includes status message722, notifying of a mismatch between the network settings of the device(e.g., 600) and the external device (e.g., 606). Device detail interface730 also includes an affordance 732 for changing the network settings ofthe external device 606 to match device 600, As shown in FIG. 7E,affordance 732 includes the text “MOVE SPEAKER TO NEW_NETWORK”, where“NEW_NETWORK” is the name of the Wi-Fi network that device 600 willconfigure device 606 to connect to (and to which device 600 is currentlyconnected).

As shown in FIG. 7E, device 600 receives user input 734 (e.g., a tap)corresponding to selection of affordance 732.

In some embodiments, a device (e.g., 600) displays an affordance (e.g.,732), for changing the network settings of an external device (e.g.,606) to match the device, at one or more of a home user interface (e.g.,700), a home status interface (e.g., 712), and a device status interface(e.g., 720). For example, affordance 732 can be displayed directly athome user interface 700, allowing the user to resolve the Wi-Fi mismatchwithout navigating to another interface.

In some embodiments, in response to selection of an affordance (e.g.,732) for changing a network setting of an external device, the device(e.g., 600) causes a network setting of the external device (e.g., 606)to be updated. For example, device 600 transmits data causing device 606to update a stored network setting in response to selection ofaffordance 732. In some embodiments, causing a network setting of theexternal device to updated comprises causing the external device toconnect to a network being used by the device (e.g., 600), that is notbeing used by the external device (e.g., 606). For example, in responseto user input selection 734 of affordance 732, device 600 causes device606 to cease being connected to “OLD_NETWORK” and to connect to“NEW_NETWORK” (which device 600 is connected to). Such an action isuseful, for example, where device 606 has been moved (e.g., taken alongwith the user while on vacation, where the user's home network is notavailable) or where device 606 was erroneously configured with incorrectnetwork information (e.g., at the time of configuration, device 600 wasinadvertently connected to a neighbor's Wi-Fi network, and thusconfigured 606 to connect to the neighbor's network rather than theuser's own home network).

FIG. 7F illustrates an exemplary device detail user interface 730displayed while the network settings of device 606 are being updated.For example, device detail user interface 730 of FIG. 7F includes themessage “UPDATING WI-FI NETWORK . . . ” and is displayed in response toreceiving user input 734 corresponding to selection of affordance 732.

FIG. 7G illustrates an exemplary device detail user interface 730displayed by a device (e.g., 600) when there is no mismatch between thenetwork settings of the device and the external device (e.g., 606). Forexample, device 600 displays interface 730 as shown in FIG. 7G inresponse to receiving user input 734 corresponding to selection ofaffordance 732 (e.g., subsequent to, or instead of, interface 730 asshown in FIG. 7F). As shown in FIG. 7G, device detail user interface 730no longer includes status message 722 notifying of the Wi-Fi mismatch.Additionally, affordance 732. is no longer displayed because the device606 is now connected to the same wireless network as device 600. Forexample, device 600 and device 606 are now both connected to thewireless network “NEW_NETWORK”, which is the preferred network becausethe user's personal device 600 (e.g., a smartphone) is connected to it.Also shown in FIG. 7G, device representation 702 no longer includesstatus message 702A (notifying of the mismatch), and now includes anormal status message associated with device 606 (e.g., the speaker ispaused).

FIGS. 7H-7J illustrate exemplary interfaces for displaying additionalinformation associated with an external device. As shown in FIG. 7H,device detail interface 730 includes a list of several options forviewing or toggling settings and information associated with device 606(e.g., “MUSIC & PODCAST” settings, “VOICE ASSISTANT” settings). In thisexample, the list is scrollable. In FIG. 7H, device 600 receives userinput 736 representing an upward swipe gesture at device detail userinterface 730.

At FIG. 7I, device 600 has scrolled the display of device detail userinterface 730 upward, in response to user input 736, to revealadditional settings and information regarding device 606. For example,device 600 now displays identifying information associated with device606 (e.g., “SERIAL NUMBER”, “MODEL”), including an identifier 738labeled “WI-FI NETWORK” that provides information regarding a wirelessnetwork that device 606 is currently connected to. As shown in FIG. 7I,identifier 738 indicates that device 606 is currently connected to theWi-Fi network with the SSID “NEW_NETWORK” (connected to in response toreceiving user input 734).

In some embodiments, an identifier (e.g., 738) of the current wirelessnetwork of the external device (e.g., 606) is selectable. For example,at FIG. 7I, device 600 receives user input 740 (e.g., a tap)representing selection of identifier 738. In some embodiments, inresponse to selection of an identifier (e.g., 738), the device displaysa media access control address (also referred to as a “MAC address” or a“Wi-Fi address”). For example, in FIG. 7J, identifier 738 has beenreplaced by identifier 742 labeled “WI-FI ADDRESS” that includes theWi-Fi address “55:55:55:55:55:55”. In this way, the user can use device600 to access this information which can be used to uniquely identifythe external device on the local area network, for example, to configurea permissions setting associated with the local area network (e.g.,configure a network router to allow the external device to connect tothe network “NEW_NETWORK”).

FIGS. 8A-8C is a flow diagram illustrating a method for 800 using anelectronic device in accordance with some embodiments. Method 800 isperformed at a device (e.g., 100, 300, 500, 580) with a display and oneor more wireless antennas. Some operations in method 800 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 800 provides an intuitive way for managingnetwork connection settings of an external device. The method reducesthe cognitive burden on a user for managing network connection settingsof an external device, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user tomanage network connection settings of an external device faster and moreefficiently conserves power and increases the time between batterycharges.

The electronic device (e.g., 600), while the electronic device isconnected, via the one or more wireless antennas, to a first local areanetwork (e.g., a first Wi-Fi network, a Wi-Fi network having a firstSSID), displays (802) a first external device management interface(e.g., 700, 712, 720, 730), wherein: the first external devicemanagement interface is associated with a first external device (e.g.,606) (e.g., a smart speaker, a smart watch, a Wi-Fi connected accessory(e.g., a connected light)) that is not connected to the first local areanetwork (e.g., the network with SSID) “NEW_NETWORK” described above withrespect to FIG. 7E) (e.g., the external device is connected to a secondlocal area network (e.g., “OLD_NETWORK” as described above) that isdifferent than the first local area network; the external device is notcurrently connected to a local area network); and the first externaldevice management interface includes a first affordance (e.g., 732 asshown in FIG. 7E).

The electronic device (e.g., 600) receives (804) a user input (e.g.,734) (e.g., a tap gesture on the affordance, a mouse click on theaffordance) corresponding to selection of the first affordance (e.g.,732 as shown in FIG. 7E).

In response to receiving the user input (e.g., 734) corresponding toselection of the first affordance (e.g., 732), the electronic device(e.g., 600) causes (806) the first external device (e.g., 606) to (e.g.,sends an instruction to the first external device to) connect to thefirst local area network (e.g., and disconnect from the second localarea network).

Causing a first external device to connect to a first location areanetwork in response to selection of an affordance at an external devicemanagement interface provides the user with an efficient means forupdating network connection settings of the external device, reducingthe number of inputs needed for doing so, and provides the user withmore control of the external device. Providing more control of theexternal device to the user enhances the operability of the externaldevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, prior to displaying the first external devicemanagement interface (e.g., 730), the electronic device (e.g., 600)receives (808) a request (e.g., user input selection of devicerepresentation 702; user input 714 or 726) to display an external devicemanagement interface (e.g., an interface for viewing and/or controllingone or more settings of an external device; the first external devicemanagement interface or an external device management interfacedifferent than the first external device management interface). Inresponse to receiving (810) the request to display the external devicemanagement interface: in accordance with a determination that a set ofnetwork condition criteria are met, the set of network conditioncriteria including a criterion that is met when the first externaldevice is connected to a local area network (e.g., “OLD_NETWORK” asdescribed above) that is different than a local area network (e.g.,“NEW_NETWORK as described above) that the electronic device is (e.g.,currently) connected to, the electronic device displays (812) the firstexternal device management interface (e.g., 730 as shown in FIG. 7E);and in accordance with a determination that the set of network conditioncriteria are not met, the electronic device displays (814) a secondexternal device management interface (e.g., 730 as shown in FIG. 7G)that does not include the first affordance (e.g., 732 is not shown inFIG. 7G) (e.g., does not include an affordance that, when selected,causes the first external device to switch to a different local areanetwork).

Displaying a first external device management interface (that includes afirst affordance) or a second external device management interface (thatdoes not include a first affordance) dependent on a determination ofwhether a set of network condition criteria are met provides the userwith feedback about the current state of the external device andprovides visual feedback to the user indicating that the networksettings associated with the external device either do or do not requireattention. Providing improved visual feedback to the user enhances theoperability of the external device and makes the user-device interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the set of network condition criteria includes acriterion that is met when the electronic device (e.g., 600) and thefirst external device (e.g., 606) satisfy a proximity requirement (e.g.,a proximity condition or threshold distance) (e.g., devices are within apredetermined distance of each other (e.g., as determined by GPS orother localization technology); the devices are within range of acommunication protocol (e.g., Bluetooth, peer-to-peer Wi-Fi) thatrequires proximity). In some embodiments, the affordance (e.g., 732) forcausing the first external device to connect to the same local areanetwork as the electronic device is not displayed if the devices are notwithin proximity of each other (e.g., interface 730 is displayed asshown in FIG. 7G, which does not include affordance 732).

Displaying a first external device management interface (that includes afirst affordance) or a second external device management interface (thatdoes not include a first affordance) dependent on a determination ofwhether a set of network condition criteria are met, wherein thecriteria include criterion met when a an electronic device and anexternal device meet a proximity condition, provides the user withfeedback about the current state of the external device and providesvisual feedback to the user indicating that the network settingsassociated with the external device either do or do not requireattention, while also preventing the display of false errors. Providingimproved visual feedback to the user enhances the operability of theexternal device and makes the user-device interface more efficient(e.g., by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first external device management interface(e.g., 730) includes a second affordance (e.g., 738). The electronicdevice (e.g., 600) receives (822) a user input (e.g., 740) correspondingto selection of the second affordance. In response to receiving the userinput corresponding to selection of the second affordance, theelectronic device displays (824) a media access control address (e.g., aWi-Fi address) of the first external device (e.g., ADDRESS55:55:55:55:55:55 as shown in identifier 742 of FIG. 7J).

In some embodiments, the second affordance (e.g., 738) includes anindication (e.g., a textual indication) of the local area network thatthe first external device (e.g., 606) is (e.g., currently) connected to(e.g., identifier 738 of FIG. 7I identifies the network named“NEW_NETWORK”), and displaying the media access control address of thefirst external device includes: replacing (826) the indication of thelocal area network that the first external device is connected to withthe media access control address of the first external device. Forexample, in response to receiving user input 740 at FIG. 7I, device 600replaces display of identifier 738 with identifier 742 as shown in FIG.7J.

In some embodiments, the first external device management interface(e.g., 730) includes a third affordance (e.g., affordances labeled“INCLUDE IN FAVORITES” or “USE LISTENING HISTORY” as shown in FIG. 7H)associated with a setting (e.g., a setting affecting the availability ofdigital assistant access from the first external device, a settingaffecting whether the first external device is designated as a favoriteexternal device; a non-local-area-network-related setting) of the firstexternal device (e.g., 606). The electronic device (e.g., 600) receivesa user input corresponding to selection of the third affordance. Inresponse to the user input corresponding to selection of the thirdaffordance, the electronic device modifies the setting of the firstexternal device (e.g., toggles the setting from a current value to amodified value, enabling or disabling a function associated with thesetting). In some embodiments, the first external device managementinterface (e.g., 730) is an interface dedicated to viewing and/orcontrolling one or more settings of (e.g., only) the first externaldevice. For example, interface 730 is dedicated to the settingsassociated specifically with device 606 (e.g., and no other devices). Insome embodiments, the third affordance includes, or corresponds to, anindication (e.g., text) of the current value of the setting (e.g.,left/right toggling affordance next to “INCLUDE IN FAVORITES” indicatesan enabled or disabled state (e.g., left or right) of the setting; the“ACCOUNT” setting includes an indication of the email address“JAPPLESEED@EMAIL.COM”).

In some embodiments, the first external device management (e.g., 700,712) interface includes an affordance (e.g., 704) associated with asecond external device (e.g., a lamp), different than the first externaldevice (e.g., 606). In some embodiments, the affordance associated withthe second external device, when selected, causes display of a userinterface for viewing and/or controlling one or more settings of thesecond external device. For example, an interface similar to 730 can bedisplayed, but dedicated to settings associated with the lampcorresponding to device representation 704. In some embodiments, theaffordance associated with the second external device, when selected,causes modification of a setting of the second electronic device. Forexample, selection (e.g., a tap) of device representation can cause thelamp to toggle being “ON” or “OFF”. In some embodiments, the firstexternal device management interface (e.g., 700, 712) is a centralizedinterface that displays the status of multiple external devices. Forexample, interfaces 700 and 712 are both centralized interfaces, whichinclude statuses corresponding to multiple external devices (e.g.,corresponding to 702 and 704).

In some embodiments, prior to displaying the first external devicemanagement interface (e.g., 730), the electronic device displays (816) athird external device management interface (e.g., 700) (e.g., an initialinterface of an external device management application), including: anindication (e.g., 706, 716) (e.g., a non-selectable textual or graphicalindicia) that one or more external devices (e.g., 606) (e.g., Wi-Ficonnectable devices) are not connected to the first local area network(e.g., the network “NEW_NETWORK” as described above).

In some embodiments, the third external device management includes(e.g., 700) a fourth affordance (e.g., 708) associated with the firstexternal device management interface (e.g., 712. 730). The electronicdevice (e.g., 600) receives (818) a user input (e.g., 710) correspondingto selection of the fourth affordance (e.g., 708). In response toreceiving the user input corresponding to selection of the fourthaffordance, the electronic device (e.g., 600) displays (820) the firstexternal device management interface (e.g., 712, 730).

In some embodiments, the first external device management (e.g., 700,712, 720, 730) interface includes (828) a second indication (e.g., 702A,706, 716, 722) (e.g., a non-selectable textual or graphical indicia)that one or more external devices (e.g., 606) (e.g., Wi-Fi connectabledevices; the first external device) are not connected to the first localarea network (e.g., the network named “NEW_NETWORK” as described above).In some embodiments, the second indication (e.g., 702A) is textualindication that is displayed as part of a graphical identifier (e.g.,702) of the external device that the indication corresponds to (e.g., atile associated with the relevant external device). In some embodiments,the second indication (e.g., 706, 716, 722) is a textual indication thatis displayed in a region dedicated to displaying status indications forexternal devices that is separate from graphical identifiers (e.g., 702,704) of those devices. For example, status messages 706, 716, and 722are displayed separate from identifiers 702 and 704 (e.g., statusmessage 716 is displayed above ATTENTION region of interface 712).

Displaying an indication that one or more external devices are notconnected to the first local area network provides the user withfeedback about the current state of one or more external devices andprovides visual feedback to the user indicating that the networksettings associated with the external device either do or do not requireattention. Providing improved visual feedback to the user enhances theoperability of the external device and makes the user-device interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, further in response to receiving the user input(e.g., 734) corresponding to selection of the first affordance (e.g.,732), the electronic device (e.g., 600) ceases to display (830) thesecond indication (e.g., 706, 716, 722) that one or more externaldevices are not connected to the first local area network. For example,in FIG. 7F and 7G, status message 722 is no longer displayed. In someembodiments, the second indication is replaced by an indication that athe local area network that the first external device is connected to isbeing updated (e.g., as shown in FIG. 7F). In some embodiments, thesecond indication is replaced by an indication of a current status ofthe first electronic device, other than a local area network connectionstatus. For example, in FIG. 7G, status message 702A is no longerdisplayed, and a status related to the playback of the device isdisplayed (“PAUSED”).

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve themanagement of network connection settings of an external deviceassociated with a user. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, twitter IDs,home addresses, data or records relating to a user's health or level offitness (e.g., vital signs measurements, medication information,exercise information), date of birth, or any other identifying orpersonal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted messages relevant to the management of networkconnection settings of an external device associated with a user.Further, other uses for personal information data that benefit the userare also contemplated by the present disclosure. For instance, healthand fitness data may be used to provide insights into a user's generalwellness, or may be used as positive feedback to individuals usingtechnology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof management of network connection settings of an external deviceassociated with a user, the present technology can be configured toallow users to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In addition to providing “opt in” and “opt out”options, the present disclosure contemplates providing notificationsrelating to the access or use of personal information. For instance, auser may be notified upon downloading an app that their personalinformation data will be accessed and then reminded again just beforepersonal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, networkmanagement notifications can be determined and delivered to users byinferring preferences based on non-personal information data or a bareminimum amount of personal information, such as the content beingrequested by the device associated with a user, other non-personalinformation available to a device management application, or publiclyavailable information.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more wireless antennas; one or more processors; and memory storingone or more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for: whilethe electronic device is connected, via the one or more wirelessantennas, to a first local area network, displaying a first externaldevice management interface, wherein: the first external devicemanagement interface is associated with a first external device that isnot connected to the first local area network; and the first externaldevice management interface includes a first affordance; receiving auser input corresponding to selection of the first affordance; inresponse to receiving the user input corresponding to selection of thefirst affordance, causing the first external device to connect to thefirst local area network.
 2. The electronic device of claim 1, the oneor more programs further including instructions for: prior to displayingthe first external device management interface, receiving a request todisplay an external device management interface; and in response toreceiving the request to display the external device managementinterface: in accordance with a determination that a set of networkcondition criteria are met, the set of network condition criteriaincluding a criterion that is met when the first external device isconnected to a local area network that is different than a local areanetwork that the electronic device is connected to, displaying the firstexternal device management interface; and in accordance with adetermination that the set of network condition criteria are not met,displaying a second external device management interface that does notinclude the first affordance.
 3. The electronic device of claim 2,wherein the set of network condition criteria includes a criterion thatis met when the electronic device and the first external device satisfya proximity requirement.
 4. The electronic device of claim 1, whereinthe first external device management interface includes a secondaffordance, the one or more programs further including instructions for:receiving a user input corresponding to selection of the secondaffordance; in response to receiving the user input corresponding toselection of the second affordance, displaying a media access controladdress of the first external device.
 5. The electronic device of claim4, wherein: the second affordance includes an indication of the localarea network that the first external device is connected to, anddisplaying the media access control address of the first external deviceincludes: replacing the indication of the local area network that thefirst external device is connected to with the media access controladdress of the first external device.
 6. The electronic device of claim1, wherein the first external device management interface includes athird affordance associated with a setting of the first external device,the one or more programs further including instructions for: receiving auser input corresponding to selection of the third affordance; and inresponse to the user input corresponding to selection of the thirdaffordance, modifying the setting of the first external device.
 7. Theelectronic device of claim 1, wherein the first external devicemanagement interface includes an affordance associated with a secondexternal device, different than the first external device.
 8. Theelectronic device of claim 1, the one or more programs further includinginstructions for: prior to displaying the first external devicemanagement interface, displaying a third external device managementinterface, including: an indication that one or more external devicesare not connected to the first local area network.
 9. The electronicdevice of claim 8, wherein the third external device management includesa fourth affordance associated with the first external device managementinterface, the one or more programs further including instructions for:receiving a user input corresponding to selection of the fourthaffordance; and in response to receiving the user input corresponding toselection of the fourth affordance, displaying the first external devicemanagement interface.
 10. The electronic device of claim 1, wherein thefirst external device management interface includes a second indicationthat one or more external devices are not connected to the first localarea network.
 11. The electronic device of claim 10, the one or moreprograms further including instructions for: further in response toreceiving the user input corresponding to selection of the firstaffordance, ceasing to display the second indication that one or moreexternal devices are not connected to the first local area network. 12.A non-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display and one or more wireless antennas, theone or more programs including instructions for: while the electronicdevice is connected, via the one or more wireless antennas, to a firstlocal area network, displaying a first external device managementinterface, wherein: the first external device management interface isassociated with a first external device that is not connected to thefirst local area network; and the first external device managementinterface includes a first affordance; receiving a user inputcorresponding to selection of the first affordance; in response toreceiving the user input corresponding to selection of the firstaffordance, causing the first external device to connect to the firstlocal area network.
 13. A method comprising: at an electronic devicewith a display and one or more wireless antennas: while the electronicdevice is connected, via the one or more wireless antennas, to a firstlocal area network, displaying a first external device managementinterface, wherein: the first external device management interface isassociated with a first external device that is not connected to thefirst local area network; and the first external device managementinterface includes a first affordance; receiving a user inputcorresponding to selection of the first affordance; in response toreceiving the user input corresponding to selection of the firstaffordance, causing the first external device to connect to the firstlocal area network.